Glossary

Bug Report

Larger projects invariable contain some ugly errors which the user may encounter at some time. In such cases, we ask that the user submit a Bug Report. This is a description of the error which has been encountered. Check the circumstances under which the error occurs and write down everything! Note the exact version of RDB-Salv which you are using and the configuration of your computer. Most significantly, note the name and version of the device driver which you are using. If you are using `scsi.device', simply type "version scsi.device full" at a CLI prompt and note the output.

Coffee Break

A coffee break is that amount of time required by a program to do a particular task in background. Most of the time, there's no precise indication of how long this is. Sometimes, it won't be long enough to get the kettle to boil, yet at other times, you'll have enough time to invite the neighbours around to share the latest gossip over some cake. I'd like to take this opportunity to apologize to those who may have been misled that a single cup of coffee was sufficient, by my comments on Meeting Pearls III. Of course, a bucket of coffee was what I meant. :-)

DeviceList

This is a system list maintained in RAM, The list contains all devices (e.g. `DF0:', `DH0:') as well as volumes and assigns known to the system. This list contains all the information required to mount devices such as `DF0:' and `DH0:'. If your RDB and associated partition blocks have been destroyed, but the devices are still mounted (if you haven't rebooted (1)), then you can salvage your partitioning data by scanning the device list for the required devices.

Device Name

The device name is the name of a partition as visible from within a prep program. `DH0:' is a typical example, whereas `Workbench:' is not a device name, being a volume name.

Disaster

A disaster is the greatest foreseeable accident. In relation to RDB-Salv, this means the destruction of the RDB and associated partition blocks. Such a disaster previously meant the loss of all data on the hard disk.

Device Unit

See Unit.

Device Driver

Every hard drive requires a Device Driver so that it can be used in the AMIGA in a system-conformant way. This driver is responsible for reading data from, and writing data to the hard disk, amongst other tasks. Devices drivers have a name ending in .device. For example; scsi.device, gvpscsi.device, omniscsi.device, z3scsi.device, dracoscsi.device, etc.

Floppy Image

Floppy disks and even partitions can be written into files by means of "unrolling" them so that the file contains blocks starting from the lowest (0) through to the highest-numbered block at the end. Such a file contains a Floppy Image. At some time thereafter, the file can be written to a floppy of equal size to yield an exact copy of the original. The floppy has, in principle, been copied. Unfortunately, RDB-Salv cannot always discriminate between data representing a real partition or just data from a Floppy Image previously stored in a file as it often looks exactly like a real partition. section Salvage describes how to get around problems caused by such a situation.

Hard Disk Parameters

The right-hand panel of the section Salvage-Page show data including hard disk parameters: Every hard disk has a fixed number of blocks on which data may be stored. These blocks are divided into Cylinders, Tracks, Heads and Sectors. A cylinder contains one or more tracks -- dependent on the number of heads (if there are two heads, then every cylinder contains two tracks, etc.). A track, in turn, consists of a number of sectors. The actual number of cylinders, heads and sectors is not important in this case. What is important, is that Cylinders×Heads×Sectors results in a number which does not exceed the total number of available blocks, and which permits a division so that all partitions can be mounted, as partition boundaries can only be specified as cylinder numbers. Most of the time, more than one combination of values gives hard disk parameters. So don't be surprised when RDB-Salv shows values which you are certain are different from the original ones. Just verify it for yourself.

Installer Script

A unified method of installation for all software packages on the AMIGA was developed to make this as simple as possible. Every package includes a plain-text file -- the Installer script --- to be interpreted by the Installer program at installation time to make the installation process as independent as possible of the prior knowledge of the user.

Management Block

These are blocks such as partition blocks, when referred to in connection with RDBs. A verbal shorthand referring to these as RDBs is, strictly speaking, incorrect. The RDB consists of a single block -- management blocks are however, all those blocks somehow linked to the RDB.

Meeting Pearls

You don't know about Meeting Pearls? That's got to be fixed straight away! Meeting Pearls is Germany's most popular CD-ROM series for the AMIGA as well as being extremely good value for money as the creators don't demand any payment for their work (2), so only direct production and distribution costs need to be paid.. If you have a CD-ROM drive, it's well worth a look.

MountList

In principle, the MountList contains the same data as partition blocks. The significant difference is that MountLists are files usually in the `DEVS:' directory and therefore readily accessible to the user. Partition blocks, in contrast, are very difficult to access for the normal user. A MountList may contain entries specifying several partitions.

Partition

Most hard disks are divided into regions (called partitions), named something like `DH0:', `wb_2.x:', `work:' etc. Sometimes, only a single such region exists. A partition can only be mounted if its precise location is known. This information can be lost in the case of a disaster. Fortunately, RDB-Salv is able to recalculate this information in just about all cases, so that the data can be salvaged.

Partition Block

Such a block is located at the start of the hard disk for (almost) every partition. It contains all the information necessary to mount the partition, e.g. the precise location of the partition. When this information has been destroyed, RDB-Salv can be used to recompute the necessary data.

Partition Boundaries

Most hard disks are divided into regions as described under Partition. The boundary between partitions is called a partition boundary.

Partition Data

Almost every partition has a partition block which describes how the partition is to be mounted. The information contained in these partition blocks is called partition data. MountLists by the way; also consist of partition data.

Prep Program

Prep programs are used to divide hard disks into regions. Well-known prep programs include HDToolBox, FaaastPrep, ExpertPrep and RD-Prep.

Program Icon

Many programs have an icon -- a small symbol on which you can click when it appears on the Workbench. Icons belonging to programs are called program icons. Further information about this can be found in your Workbench manual.

Progress Indicator

The progress indicator indicates what proportion of work has been done by the use of a bar graph. On occasions, this indicator will move at a very uneven rate. This will always occur if the it wasn't possible to pre-compute how long the particular operation would take.

Pseudo Partition

A partition which isn't normally shown when using HDToolBox or other prep programs.

RigidDiskBlock

RDB

RDSK

The RDB is a single block which resides somewhere in the first 16 blocks of a hard disk and contains information about the hard disk. It contains, amongst other things, the location of partition blocks. Contrary to common usage, the RDB, RDSK or RigidDiskBlock is always only one block, and thus doesn't include partitioning and other management blocks.

RDB Data

RDB data includes not only the data of the RDB, but also that of associated blocks, like partition blocks.

Region

See Partition.

System Partition

Almost every AMIGA which has a hard disk, has such a partition. It's the partition from which the machine is booted, and it's often called something like `wb_2.x:', `SYS' or `System:'.

UNUSED<n>

RDB-Salv chooses this volume name for all parts of the hard disk which are unused. This name is used not only when partition blocks or MountLists are written, but also when volumes are mounted.

Unit

A particular hard disk drive is identified by its unit or device unit. Valid unit numbers are typically between 0 and 6 for SCSI drives. If you have an external drive, this may have a switch for setting a number. The number is usually the unit number of the drive. If in doubt about the unit number, consult the manual for your hard disk system.

Volume Name

The formatted name of the partition is the volume name. This name is also visible on the Workbench screen and can be changed at almost any time (3) using Workbench Rename ... menu function. `Workbench' is a typical volume name, whereas `DH0:' is not; that being the device name.

Work-Partition

Most hard disk on the AMIGA are divided into at least two regions. One of these partitions -- the Work-Partition -- contains user-dependent data, like special programs, projects created by the user, etc. This partition is usually called `work:'.